Automated system for adapting market data and producing metric values

ABSTRACT

A system includes a server that implements a governing logic component and a production component. When implementing an evaluation service, the production component obtains time-dependent metric data that comprises market reference data for one or more items in the marketplace having attributes that are responsive to attributes identified for a target item. The production component discovers at least one relationship comprising a difference for a responsive marketplace item and the target item, which enables the governing logic component to contextually define context-specific instructions for adapting the market reference data for the differing marketplace item. At least one adjustment value applied to the market reference data for the responsive marketplace item automatically transforms the market reference data into normalized metric data for the target item, and produces, for the target item, one or more metrics that pertain to the evaluation service, using, at least in part, the normalized metric data.

BACKGROUND Technical Field

The present disclosure generally relates to normalizing diverse market transaction data, and more particularly, to producing one or more metric values for a target item using at least in part the normalized market transaction data for the target item.

Description of the Related Art

Commodity items such as lumber, agricultural products, metals, and livestock/meat are usually traded in the open market between a number of buyers and sellers. The sales transactions of most commodity items involve a number of parameters. For instance, in the trade of commodity lumber, a buyer usually orders materials by specifying parameters such as lumber species, grade, size (i.e., 2×4, 2×10, etc.), and length, as well as the “tally” or mix of units of various lengths within the shipment, method of transportation (i.e., rail or truck), shipping terms (i.e., FOB or delivered), and desired date of receipt, with each parameter influencing the value of the commodity purchase. Given the multiple possible combinations of factors, a commodity buyer often finds it difficult to objectively compare similar but unequal offerings among competing vendors.

For example, in a case where a lumber buyer desires to order a railcar load of spruce (SPF) 2×4's of #2 & Better grade, the buyer would query vendors offering matching species and grade carloads seeking the best match for the buyer's need or tally preference at the lowest market price. Lumber carloads are quoted at a price per thousand board feet for all material on the railcar. When the quoted parameters are not identical, it is very difficult for buyers to determine the comparative value of unequal offerings.

Typically, a lumber buyer will find multiple vendors each having different offerings available. For example, a railcar of SPF 2×4's may be quoted at a rate of $300/MBF (thousand board feet) by multiple vendors. Even though the MBF price is equal, one vendor's carload may represent significantly greater marketplace value because it contains the more desirable lengths of 2×4's, such as market-preferred 16-foot 2×4's. When the offering price varies in addition to the mix of lengths, it becomes increasingly difficult to compare quotes from various vendors. Further, because construction projects often require long lead times, the lumber product may need to be priced now, but not delivered until a time in the future. Alternately, another species of lumber (i.e., southern pine) may represent an acceptable substitute.

Therefore, from the foregoing, there is a need for a method and system that allows users to evaluate and effectively compare items having different attributes to optimize decision making with regard to such items.

BRIEF SUMMARY

The present disclosure is directed, at least in part, to normalizing diverse market reference data for a marketplace item into normalized metric data for a target item, and producing one or more metric values for the target item using at least in part the normalized metric data. More particularly, in various embodiments, described herein is a system that operates in a networked environment. It at least one aspect, the system comprises at least one server that includes a network interface, a non-transitory computer-readable medium having computer-executable instructions stored thereon, and a processor in communication with the network interface and the computer-readable medium. The processor is configured to execute the computer-executable instructions stored on the computer-readable medium. When executed, the computer-executable instructions implement system components including at least a governing logic component comprising a metric server adapter and a production component comprising a metrics application.

The metric server adapter is programmed to manage a plurality of predefined instructions that pertain to at least one evaluation service or to metric data used to provide the evaluation service, including domain or industry or user-agent specific instructions, and to define context-specific instructions for adapting the metric data. The metrics application is programmed to manage the execution of the evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the server.

At a predefined time or interval of time or in response to a triggering event, the server implements the at least one evaluation service. This causes the production component to obtain time-dependent metric data from at least one data source accessible to the at least one server. The metric data comprises market reference data, including price data, for one or more items in a marketplace, the one or more marketplace items having attributes that are responsive to attributes identified for a target item defined by a set of attributes that includes two or more parameter values.

The production component evaluates the attributes of each responsive marketplace item relative to the set of attributes that define the target item to dynamically discover relationships within the attribute data. Discovery of at least one relationship comprising a difference enables the governing logic component to contextually define one or more context-specific instructions for adapting the market reference data for a marketplace item having attributes that differ by at least one parameter value from the corresponding attributes identified for the target item.

The production component executes the context-specific instructions, including at least one context-specific instruction that causes one or more adjustment values to be applied to the market reference data for at least one marketplace item that differs. Application of the adjustment values transforms the market reference data for the responsive item into normalized metric data for the target item.

The production component produces, for the target item, one or more metric values for one or more metrics that pertain to the at least one evaluation service. Each metric value is produced, at least in part, using the normalized metric data for the target item.

In another aspect, disclosed herein is a method that includes obtaining, by at least one server, time-dependent metric data from at least one data source accessible to the server. The server operates under control of computer-executable instructions that, when executed by a processor, implement a plurality of system components including at least a governing logic component and a production component. The obtained metric data comprises market reference data, including price data, for one or more items in a marketplace, the one or more marketplace items having attributes that are responsive to attributes identified for a target item defined by a set of attributes that includes two or more parameter values.

The method further includes implementing, by the production component, at least one evaluation service. In operation, this includes evaluating the attributes of each marketplace item relative to dynamically discover relationships within the attribute data. Discovery of at least one relationship comprising a difference enables the governing logic component to contextually define one or more context-specific instructions for adapting the market reference data for a marketplace item having attributes that differ by at least one parameter value from the corresponding attributes identified for the target item.

The context-specific instructions are executed, wherein execution of at least one context-specific instruction causes one or more adjustment values to be applied to the market reference data for the marketplace item that differs. Application of the adjustment values transforms the market reference data for the marketplace item into normalized metric data for the target item.

The method also includes producing, for the target item, one or more metric values for one or more metrics that pertain to the at least one evaluation service. Each metric value is produced, at least in part, using the normalized metric data for the target item.

In yet another aspect, disclosed herein is a non-transitory computer-readable medium having computer-executable instructions stored thereon for use in a networked environment including at least one server. The server operates under control of computer-executable instructions that, when executed by a processor, implement system components including a governing logic component and a production component and causes the server to perform operations that include obtaining time-dependent metric data from at least one data source accessible to the server. The obtained metric data comprises market reference data, including price data, for one or more items in the marketplace. The responsive marketplace items have attributes that are responsive to attributes identified for a target item defined by a set of attributes that includes two or more parameter values.

The server is further caused to perform operations that include implementing at least one evaluation service. The computer-executable instructions cause the production component to evaluate the attributes of each marketplace item relative to the set of attributes that define the target item to dynamically discover relationships within the attribute data. Discovery at least one relationship comprising a difference enables the governing logic component to contextually define one or more context-specific instructions for adapting the market reference data for a marketplace item.

The production component executes the transaction-specific instructions. Execution of at least one transaction-specific instruction causes one or more adjustment values to be applied to the market reference price data for at least one responsive item having an attribute that differs by at least one parameter value from the corresponding attribute of the target item, transforming the market reference data for the responsive item into normalized metric data for the target item having attributes that differ by at least one parameter value from the corresponding attributes identified for the target item.

The production component further produces, for the target item, one or more metric values for one or more metrics that pertain to the at least one evaluation service. Each metric value is produced, at least in part, using the normalized metric data for the target item.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of the present disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram of a prior art representative portion of the Internet;

FIG. 2 is a pictorial diagram of a system of devices connected to the Internet, which depict the travel route of data;

FIG. 3 is a block diagram of the several components of the buyer's computer shown in FIG. 2 that is used to request information on a particular route;

FIG. 4 is a block diagram of the several components of an information server shown in FIG. 2 that is used to supply information on a particular route;

FIG. 5 is a flow diagram illustrating the logic of a routine used by the information server to receive and process the buyer's actions;

FIGS. 6A-6B are flow diagrams illustrating another embodiment of the logic used by the information server to receive and process the quotes and quote requests of both buyers and vendors;

FIG. 7 is a flow diagram illustrating another embodiment of the logic used by the information server to execute the process of a catalog purchase;

FIGS. 8A-8D are images of windows produced by a Web browser application installed on a client computer accessing a server illustrating one embodiment of the present disclosure; and

FIG. 9 is a flow diagram illustrating one embodiment of the normalization process described herein.

DETAILED DESCRIPTION

The term “Internet” refers to the collection of networks and routers that use the Internet Protocol (IP) to communicate with one another. A representative section of the Internet 100 as known in the prior art is shown in FIG. 1 in which a plurality of local area networks (LANs) 120 and a wide area network (WAN) 110 are interconnected by routers 125. The routers 125 are generally special-purpose computers used to interface one LAN or WAN to another. Communication links within the LANs may be twisted wire pair, or coaxial cable, while communication links between networks may utilize 56 Kbps analog telephone lines, or 1 Mbps digital T-1 lines, and/or 45 Mbps T-3 lines. Further, computers and other related electronic devices can be remotely connected to either the LANs 120 or the WAN 110 via a modem and temporary telephone link. Such computers and electronic devices 130 are shown in FIG. 1 as connected to one of the LANs 120 via dotted lines. It will be appreciated that the Internet comprises a vast number of such interconnected networks, computers, and routers and that only a small representative section of the Internet 100 is shown in FIG. 1.

The World Wide Web (WWW), on the other hand, is a vast collection of interconnected, electronically stored information located on servers connected throughout the Internet 100. Many companies are now providing services and access to their content over the Internet 100 using the WWW. In accordance with the present disclosure, and as shown in FIG. 2, there may be a plurality of buyers operating a plurality of client computing devices 235. FIG. 2 generally shows a system 200 of computers and devices to which an information server 230 is connected and to which the buyers' computers 235 are also connected. Also connected to the Internet 100 is a plurality of computing devices 250 associated with a plurality of sellers. The system 200 also includes a communications program, referred to as CEA, which is used on the sellers' computing devices 250 to create a communication means between the sellers' backend office software and the server applications.

The buyers of a market commodity may, through their computers 235, request information about a plurality of items or order over the Internet 100 via a Web browser installed on the buyers' computers. Responsive to such requests, the information server 230, also referred to as a server 230, may combine the first buyer's information with information from other buyers on other computing devices 235. The server 230 then transmits the combined buyer data to the respective computing devices 250 associated with the plurality of sellers. Details of this process are described in more detail below in association with FIGS. 5-7.

Those of ordinary skill in the art will appreciate that in other embodiments of the present disclosure, the capabilities of the server 230 and/or the client computing devices 235 and 250 may all be embodied in the other configurations. Consequently, it would be appreciated that in these embodiments, the server 230 could be located on any computing device associated with the buyers' or sellers' computing devices. Additionally, those of ordinary skill in the art will recognize that while only four buyer computing devices 235, four seller computing devices 250, and one server 230 are depicted in FIG. 2, numerous configurations involving a vast number of buyer and seller computing devices and a plurality of servers 230, equipped with the hardware and software components described below, may be connected to the Internet 100.

FIG. 3 depicts several of the key components of the buyer's client computing device 235. As known in the art, client computing devices 235 are also referred to as “clients” or “devices,” and client computing devices 235 also include other devices such as palm computing devices, cellular telephones, or other like forms of electronics. A client computing device can also be the same computing device as the server 230. An “agent” can be a person, server, or a client computing device 235 having software configured to assist the buyer in making purchasing decisions based on one or more buyer-determined parameters. Those of ordinary skill in the art will appreciate that the buyer's computer 235 in actual practice will include many more components than those shown in FIG. 3. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. As shown in FIG. 3, the buyer's computer includes a network interface 315 for connecting to the Internet 100. Those of ordinary skill in the art will appreciate that the network interface 315 includes the necessary circuitry for such a connection and is also constructed for use with TCP/IP protocol.

The buyer's computer 235 also includes a processing unit 305, a display 310, and a memory 300, all interconnected along with the network interface 315 via a bus 360. The memory 300 generally comprises a random access memory (RAM), a read-only memory (ROM), and a permanent mass storage device, such as a disk drive. The memory 300 stores the program code necessary for requesting and/or depicting a desired route over the Internet 100 in accordance with the present disclosure. More specifically, the memory 300 stores a Web browser 330, such as Netscape's NAVIGATOR® or Microsoft's INTERNET EXPLORER® browsers, used in accordance with the present disclosure for depicting a desired route over the Internet 100. In addition, memory 300 also stores an operating system 320 and a communications application 325. It will be appreciated that these software components may be stored on a computer-readable medium and loaded into memory 300 of the buyers' computer 235 using a drive mechanism associated with the computer-readable medium, such as a floppy, tape, or CD-ROM drive.

As will be described in more detail below, the user interface which allows products to be ordered by the buyers are supplied by a remote server, i.e., the information server 230 located elsewhere on the Internet, as illustrated in FIG. 2. FIG. 4 depicts several of the key components of the information server 230. Those of ordinary skill in the art will appreciate that the information server 230 includes many more components than shown in FIG. 4. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. As shown in FIG. 4, the information server 230 is connected to the Internet 100 via a network interface 410. Those of ordinary skill in the art will appreciate that the network interface 410 includes the necessary circuitry for connecting the information server 230 to the Internet 100, and is constructed for use with TCP/IP protocol.

The information server 230 also includes a processing unit 415, a display 440, and a mass memory 450, all interconnected along with the network interface 410 via a bus 460. The mass memory 450 generally comprises a random access memory (RAM), read-only memory (ROM), and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof. The mass memory 450 stores the program code and data necessary for incident and route analysis as well as supplying the results of that analysis to consumers in accordance with the present disclosure. More specifically, the mass memory 450 stores a metrics application 425 formed in accordance with the present disclosure for managing the purchase forums of commodities products, and a metric server adapter 435 for managing metric data and the logic for adapting the metric data. In addition, the mass memory 450 stores a database 445 of buyer information continuously logged by the information server 230 for statistical market analysis. It will be appreciated by those of ordinary skill in the art that the database 445 of product and buyer information may also be stored on other servers or storage devices connected to either the information server 230 or the Internet 100. Finally, the mass memory 450 stores Web server software 430 for handling requests for stored information received via the Internet 100 and the WWW, and an operating system 420. It will be appreciated that the aforementioned software components may be stored on a computer-readable medium and loaded into the mass memory 450 of the information server 230 using a drive mechanism associated with the computer-readable medium, such as floppy, tape, or CD-ROM drive. In addition, the data stored in the mass memory 450 and other memory can be “exposed” to other computers or persons for purposes of communicating data. Thus, “exposing” data from a computing device could mean transmitting data to another device or person, transferring XML data packets, transferring data within the same computer, or other like forms of data communications.

In accordance with one embodiment of the present disclosure, FIG. 5 is a flow chart illustrating the logic implemented for the creation of a Request for Quote (RFQ) by a singular buyer or a pool of buyers. In process of FIG. 5, also referred to as the pooling process 500, a buyer or a pool of buyers generate an RFQ which is displayed or transmitted to a plurality of sellers. Responsive to receiving the RFQ, the sellers then send quotes to the buyers.

In summary, the creation of the RFQ consists of at least one buyer initially entering general user identification information to initiate the process. The buyer would then define a Line Item on a Web page displaying an RFQ form. The Line Item is defined per industry specification and units of product are grouped as a “tally” per industry practice. The pooling process 500 allows buyers to combine RFQ Line Items with other buyers with like needs. In one embodiment, the pool buy feature is created by a graphical user interface where the RFQ Line Items from a plurality of buyers are displayed on a Web page to one of the pool buyers, referred to as the pool administrator. The server 230 also provides a Web-based feature allowing the pool administrator to selectively add each RFQ Line Item to one combined RFQ. The combined RFQ is then sent to at least one vendor or seller. This feature provides a forum for pooling the orders of many buyers, which allows individual entities or divisions of larger companies to advantageously bid for larger orders, thus providing them with more bidding power and the possibility of gaining a lower price.

The pooling process 500 begins in step 501 where a buyer initiates the process by providing buyer purchase data. In step 501, the buyer accesses a Web page transmitted from the server 230 configured to receive the buyer purchase data, also referred to as the product specification data set or the Line Item data. One exemplary Web page for the logic of step 501 is depicted in FIG. 8A. As shown in FIG. 8A, the buyer enters the Line Item data specifications in the fields of the Web page. The Line Item data consists of lumber species and grade 803, number of pieces per unit 804, quantities of the various units comprising the preferred assortment in the tally 805A-E, delivery method 806, delivery date 807, delivery location 808, and the overall quantity 809. In one embodiment, the buyer must define the delivery date as either contemporaneous “on-or-before” delivery date or specify a delivery date in the future for a “Forward Price” RFQ. In addition, the buyer selects a metric or multiple metrics in a field 810 per RFQ Line Item (tally). As described in more detail below, the metric provides pricing data that is used as a reference point for the buyer to compare the various quotes returned from the sellers. The buyer RFQ Line Item data is then stored in the memory of the server 230.

Returning to FIG. 5, at a next step 503, the server 230 determines if the buyer is going to participate in a pool buy. In the process of decision block 503, the server 230 provides an option in a Web page that allows the buyer to post their Line Item data to a vendor or post their Line Item data to a buyer pool. The window illustrated in FIG. 8A is one exemplary Web page illustrating these options for a buyer. As shown in FIG. 8A, the links “Post Buyer Pool” 812 and “Post to Vendors” 814 are provided on the RFQ Web page.

At step 503, if the buyer does not elect to participate in a pool buy, the process continues to step 513 where the server 230 generates a request for a quote (RFQ) from the buyer's Line Item data. A detailed description of how the server 230 generates a request for a quote (RFQ) is summarized below and referred to as the purchase order process 600A depicted in FIG. 6A.

Alternatively, at decision block 503, if the buyer elects to participate in a pool buy, the process continues to step 505 where the system notifies other buyers logged into the server 230 that an RFQ is available in a pool, allowing other buyers to add additional Line Items (tallies) to the RFQ. In this part of the process, the Line Items from each buyer are received by and stored in the server memory. The Line Items provided by each buyer in the pool are received by the server 230 using the same process as described above with reference to block 501 and the Web page of FIG. 8A. All of the Line Items stored on the server 230 are then displayed to a pool administrator via a Web page or an e-mail message. In one embodiment, the pool administrator is one of the buyers in a pool where the pool administrator has the capability to select all of the Line Item data to generate a combined RFQ. The server 230 provides the pool administrator with this capability by the use of any Web-based communicative device, such as e-mail or HTML forms. As part of the process, as shown in steps 507 and 509, the pool may be left open for a predetermined period of time to allow additional buyers to add purchase data to the current RFQ.

At decision block 509, the server 230 determines if the pool administrator has closed the pool. The logic of this step 509 is executed when the server 230 receives the combined RFQ data from the pool administrator. The pool administrator can send the combined RFQ data to the server 230 via an HTML form or by other electronic messaging means such as e-mail or URL strings. Once the server 230 has determined that the pool is closed, the process continues to block 510 where the Line Items from each buyer (the combined RFQ) are sent to all of the buyers in the pool. The process then continues to step 513 where the server 230 sends the combined RFQ to the vendors or sellers.

Referring now to FIG. 6A, one embodiment of the purchase-negotiation process 600 is disclosed. The purchase-negotiation process 600 is also referred to as a solicited offer process or the market purchase process. In summary, the purchase-negotiation process 600 allows at least one buyer to submit an RFQ and then view quotes from a plurality of vendors and purchase items from selected vendor(s). The logic of FIG. 6A provides buyers with a forum that automatically manages, collects, and normalizes the price of desired commodity items. The purchase-negotiation process 600 calculates a normalized price data set that is based on a predefined metric(s). The calculation of the normalized price data set in combination with the format of the Web pages described herein create an integrated forum where quotes for a plurality of inherently dissimilar products can be easily obtained and compared.

The purchase-negotiation process 600 begins at step 601 where the RFQ, as generated by one buyer or a pool of buyers in the process depicted in FIG. 5, is sent to a plurality of computing devices 250 associated with a plurality of sellers or vendors. The vendors receive the RFQ via a Web page transmitted by the server 230. In one embodiment, the vendors receive an e-mail message having a hypertext link to the RFQ Web page to provide notice to the vendor. Responsive to the information in the buyers' RFQ, the process then continues to step 603 where at least one vendor sends their quote information to the server 230.

In the process of step 603, the vendors respond to the RFQ by sending their price quote to the server 230 for display via a Web page to the buyer or buyer pool. Generally described, the vendors send an HTML form or an e-mail message with a price and description of the order. The description of the order in the quote message contains the same order information as the RFQ.

FIG. 8B illustrates one exemplary Web page of a vendor quote that is displayed to the buyer. As shown in FIG. 8B, the vendor quote includes the vendor's price 813, the lumber species and grade 803, number of pieces per unit 804, quantities of the various units comprising the preferred assortment in the tally 805A-E, delivery method 806, delivery date 807, and delivery location 808. In the quote response message, the vendor has the capability to modify any of the information that was submitted in the RFQ. For example, the vendor may edit the quantity values for the various units comprising the preferred assortment in the tally 805A-E. This allows the vendor to adjust the buyer's request according to the vendor's inventory, best means of transportation, etc. All of the vendor's quote information is referred to as price data set or the RFQ Line Item (tally) quote.

Returning to FIG. 6A, the process continues to step 605, where the server 230 normalizes the price of each RFQ Line Item (tally) quote from each vendor. The normalization of the vendor's price is a computation that evaluates the vendor's price utilizing data from a metric. The normalization process is carried out because each vendor may respond to the Line Items of an RFQ by quoting products that are different from a buyer's RFQ and/or have a different tally configuration. The normalization of the metric pricing allows the buyers to objectively compare the relative value of the different products offered by the plurality of vendors. For example, one vendor may produce a quote for an RFQ of one unit of 2×4×10, two units of 2×4×12, and three units of 2×4×16. At the same time, another vendor may submit a quote for three units of 2×4×10, one unit of 2×4×12, and two units of 2×4×16. Even though there is some difference between these two offerings, the price normalization process provides a means for the buyer to effectively compare and evaluate the different quotes even though there are variations in the products. The price normalization process 900 is described in more detail below in conjunction with the flow diagram of FIG. 9.

Returning again to FIG. 6A, at step 607 the vendor's quote information is communicated to the buyer's computer for display. As shown in FIG. 8B and described in detail above, the vendor's quote is displayed via a Web page that communicates the vendor's quote price 813 and other purchase information. In addition, the vendor's quote page contains a metric price 815 and a quote price versus metric price ratio 816. The metric price 815 and the quote price versus metric price ratio 816 are also referred to as a normalized price data value. A ratio higher than one (1) indicates a quote price that is above the metric price, and a lower ratio indicates a quote price that is below the metric price.

Next, at step 609, the buyer or the administrator of the buyer pool compares the various products and prices quoted by the vendors along with the normalized price for each Line Item on the RFQ. In this part of the process, the buyer may decide to purchase one of the products from a particular vendor and sends a notification to the selected vendor indicating the same. The buyer notifies the selected vendor by the use of an electronic means via the server 230, such as an HTML form, a chat window, e-mail, etc. For example, the quote Web page depicted in FIG. 8B shows two different quotes with two different tallies, the first quote price 813 of $360, and the second quote price 813A of $320. If the buyer determines that they prefer to purchase the materials listed in the first quote, the buyer selects the “Buy!” hyperlink 820 or 820A associated with the desired tally.

If the buyer is not satisfied with any of the listed vendor quotes, the server 230 allows the buyer to further negotiate with one or more of the vendors to obtain a new quote. This step is shown in decision block 611, where the buyer makes the determination to either accept a quoted price or proceed to step 613 where they negotiate with the vendor to obtain another quote or present a counter-offer. Here, the server 230 provides a graphical user interface configured to allow the buyer and one vendor to electronically communicate, using, e.g., a chat window, streaming voice communications, or other standard methods of communication. There are many forms of electronic communications known in the art that can be used to allow the buyer and vendors to communicate.

The buyer and seller negotiate various quotes and iterate through several steps 603-613 directed by the server 230, where each quote is normalized, compared, and further negotiated until a quote is accepted by the buyer or negotiations cease. While the buyer and seller negotiate the various quotes, the server 230 stores each quote until the two parties agree on a price. At any step during the negotiation process, the system always presents the buyer with an option to terminate the negotiation if dissatisfied with the quote(s).

At decision block 611, when a buyer agrees on a quoted price, the process then continues to step 615 where the buyer sends a notification message to the vendor indicating they have accepted a quote. As described above with reference to steps 603-613, the buyer notification message of step 615 may be in the form of a message on a chat window, e-mail, by an HTML form, or the like. However, the buyer notification must be transmitted in a format that allows the system to record the transaction. The buyer notification may include all of the information regarding the specifications by RFQ Line Item, such as, but not limited to, the buy price, date, and method of shipment, and payment terms.

The purchase-negotiation process 600 is then finalized when the system, as shown in step 617, sends a confirmation message to a tracking system. The confirmation message includes all of the information related to the agreed sales transaction.

Optionally, the process includes step 619, where the server 230 stores all of the information related to RFQ, offers, and the final sales transaction in a historical database. This would allow the server 230 to use all of the transaction information in an analysis process for providing an improved method of obtaining a lower market price in future transactions and in identifying optimum purchasing strategy. The analysis process is described in further detail below. Although the illustrated embodiment is configured to store the data related to the sales transactions, the system can also be configured to store all of the iterative quote information exchanged between the buyer and vendor.

Referring now to FIG. 6B, an embodiment of the unsolicited offer process 650 is disclosed. In summary, the unsolicited offer process 650, also referred to as the unsolicited market purchase process, allows at least one buyer to view unsolicited offers from a plurality of vendors and purchase items from a plurality of vendors from the offers. The logic of FIG. 6B provides buyers with a forum that automatically manages, collects, and normalizes price quotes based on metric data. By the price normalization method of FIG. 6B, the server 230 creates an integrated forum where offers for a plurality of inherently dissimilar products can be obtained and normalized for determination of a purchase.

The unsolicited offer process 650 begins at step 651 where the plurality of vendors is able to submit offers to the server 230. This part of the process is executed in a manner similar to step 603 of FIG. 6A, where the vendor submits a quote to the server 230. However, in the Web page of step 651, the server 230 generates a Web page containing several tallies from many different vendors. In addition, at step 651, the server 230 stores all of the unsolicited offer data provided by the vendors.

Next, at step 653, a buyer views the offers stored on the server 230. This part of the process is carried out in a manner similar to the process of step 603 or 607 where the server 230 displays a plurality of offers similar to the tallies depicted in FIG. 8A.

Next, at step 655, the buyer selects a metric for the calculation of the normalized price associated with the selected offer. As described in more detail below, metric data may come from publicly available information, i.e., price of futures contracts traded on the Chicago Mercantile Exchange, subscription services such as Crowes™ or Random Lengths™ processed via the metric server adapter 435 (shown in FIG. 4), or internally generated metrics derived from the data stored in the server 230. The normalization calculation, otherwise referred to as the normalization process, occurs each time the buyer views a different offer, and the normalization calculation uses the most current metric data for each calculation. The normalization process is carried out because each vendor will most likely offer products that may vary from products of other vendors and have a different tally configuration from those supplied by other vendors. The normalization of the metric pricing allows the buyers to compare the relative value of the different products offered by the number of vendors. The metric price for each selected offer is displayed in a similar manner as the metric price 815 and 816 shown in the Web page of FIG. 8B.

Next, at decision block 657, the buyer selects at least one offer for purchase. This is similar to the process of FIG. 6A in that the buyer selects the “Buy!” hyperlink 820 associated with the desired tally to purchase an order. The process then continues to steps 659-663, where, at step 659, the process transmits a buy notice to the vendor, then, at step 661, sends a purchase confirmation to the tracking system, and then, at step 663, saves the transaction data in the server database. The steps 659-663 are carried out in the same manner as the steps 615-619 of FIG. 6A. In the above-described process, the buyer notification may include all of the information regarding the specifications by RFQ Line Item, and data such as, but not limited to, the buy price, date, and method of shipment, and the payment terms.

Referring now to FIG. 7, a flow diagram illustrating yet another embodiment of the present disclosure is shown. FIG. 7 illustrates the catalog purchase process 700. This embodiment allows buyers to search for a catalog price of desired commerce items, enter their purchase data based on the pre-negotiated catalog prices, and to compare those catalog prices with a selected metric price and the current market price, wherein the current market price is determined by the purchase-negotiation process 600.

The process starts at step 701 where the buyer selects a program buy catalog 443. The program buy catalog 443 provides buyers with the published or pre-negotiated price of the desired products. Next, at step 703, based on the catalog information, the buyer then enters their purchase data. Similar to step 501 of FIG. 5 and the tally shown in FIG. 8A, the buyer sends purchase data to the server 230, such as the desired quantity of each item and the lumber species, grade, etc.

The process then proceeds to decision block 707 where the buyer makes a determination of whether to purchase the items using the catalog price or purchase the desired product in the open market. Here, the server 230 allows the user to make this determination by displaying the metric price of each catalog price. This format is similar to the metric price 815 and 816 displayed in FIG. 8B.

At decision block 707, if the buyer determines that the catalog price is better than a selected metric price, the process then proceeds to steps 709, 711, and 713, where a program buy from the catalog is executed, and the buyer's purchase information is stored on the server 230 and sent to the vendor's system to confirm the sale. These steps 711-713 are carried out in the same manner as the confirmation and save steps 617 and 619 as shown in FIG. 6A.

At decision block 707, if the buyer determines that the metric price is better than the catalog price, the process continues to step 717 where the buyer's purchase data is entered into an RFQ. At this step, the process carries out the first five steps 601-609 of the method of FIG. 6A to provide buyers with the price data from the open market, as well as provide the normalized prices for each open market quote. At step 719, the server 230 then displays a Web page that allows the user to select from a purchase option of a catalog or spot (market) purchase. At decision block 721, based on the displayed information, the buyer will then have an opportunity to make a determination of whether they will proceed with a catalog purchase or an open market purchase.

At decision block 721, if the buyer proceeds with the catalog purchase, the process continues to step 709 where the catalog purchase is executed. Steps 709-713 used to carry out the catalog purchase are the same as if the buyer had selected the catalog purchase in step 707. However, if at decision block 721 the buyer selects the option to proceed with the market purchase, the process continues to step 723 where the RFQ generated in step 717 is sent to the vendor. Here, the process carries out the steps of FIG. 6 to complete the open market purchase. More specifically, the process continues to step 609 where the buyer compares the normalized prices from each vendor. Once a vendor is selected, the negotiation process of steps 603-613 is carried out until the buyer decides to execute the purchase. Next, the transaction steps 615-619 are carried out to confirm the purchase, notify the tracking system, and save the transactional data on the historical database.

Optionally, the process can include a step where the server 230 stores all of the information related to program buy and metric comparisons and the final sales transaction in a historical database. This would allow the server 230 to use all of the transaction information in an analysis process for providing an improved method of obtaining the value of the program. Although the illustrated embodiment is configured to store the data related to the sales transactions, the system can also be configured to store all of the iterative quote information exchanged between the buyer and vendor.

The analysis process allows the server 230 to utilize the sales history records stored in steps 619 and 711 to generate price reports for communication to various third parties as well as provide a means of calculating current market prices for products sold in the above-described methods. The sales history records are also used as the source for a metric, such as those used in the process of FIGS. 6A, 6B, and 7. As shown in steps 619, 663, and 711, the server 230 continually updates the historical database for each sales transaction. The analysis reporting process allows a buyer or manager of buyers to conduct analysis on the historical information. This analysis would include multi-value cross compilation for purposes of determining purchasing strategies, buyer effectiveness, program performance, vendor performance, and measuring effectiveness of forward pricing as a risk management strategy.

Referring now to FIG. 9, a flow diagram illustrating the logic of the normalization process 900 is shown. The logic of the normalization process 900 resides on the server 230 and processes the quotes received from commodity sellers. The logic begins at step 905 where quote data is obtained from the seller in response to the buyer's RFQ as described above.

Next, at step 910, routine 900 iteratively calculates the board footage (BF) of each type of lumber. Once all the totals are calculated for each type, routine 900 continues to step 915 where the server 230 calculates the total type price.

At step 915, routine 900 iteratively calculates the total type price for the amount of each type of lumber specified in the quote. This is accomplished by taking the total board footage (BF) calculated in block 910 and multiplying the total BF by the price per MBF specified in the quote. Once all the prices are calculated for each type, routine 900 continues to step 920 where the server 230 calculates the total quoted price. At step 920, the routine 900 calculates the total price for the quote by summing all of the total type prices calculated at step 915.

At step 925, the routine 900 iteratively retrieves the most current price for each type of lumber specified in the quote from a predefined metric source(s). Metric data may come from publicly available information, i.e., price of futures contracts traded on the Chicago Mercantile Exchange, subscription service publications such as Crowes™ or Random Lengths™ processed via the metric server adapter 435 (shown in FIG. 4), or internally generated metrics derived from the server database. Once all the prices are retrieved for each type, at step 930, the routine 900 then iteratively calculates the market price for the quantity of each type of lumber in the quote. Once the totals for all types are calculated, the routine 900 continues to step 935 where the routine 900 calculates the total market price for the quote by summing all the most current prices calculated in step 930. Although this example illustrates that steps 910-920 are executed before steps 925-935, these two groups of steps can be executed in any order, or in parallel, so long as they are both executed before a comparison step 940.

At step 940, routine 900 compares the total quoted to the metric price to arrive at a comparative value. In one exemplary embodiment of the current invention, the comparative value is a “percent of metric” value. A value higher than one hundred (100) percent indicates a price that is above the metric rate, and a lower percent indicates a price that is below the metric rate.

The operation of routine 900 can be further illustrated through an example utilizing specific exemplary data. In the example, a buyer sends out a request for a quote (RFQ) requesting a lot of 2×4 S&B lumber consisting of five units of 2″×4″×8′, two units of 2″×4″×14′, and five units of 2″×4″×16′. The buyer then receives quotes from three sellers. Seller A responds with a tally of six units of 2″×4″×8′, four units of 2″×4″×14′, and three units of 2″×4″×16′ for $287 per thousand board feet. Seller B responds with a lot of five units of 2″×4″×8′, one unit of 2″×4″×14′, and six units of 2″×4″×16′ for $283 per thousand board feet. Seller C responds with a lot of one unit of 2″×4″×8′, five units of 2″×4″×14′, and five units of 2″×4″×16′ for $282 per thousand board feet. Suppose also that the typical unit size is 294 pieces/unit, and the metric or reported market price for 2″×4″×8's is $287.50, for 2″×4″×14's is $278.50, and for 2″×4″×16′ is $288.

Viewing the MBF prices for the respective quotes is not particularly informative, given that certain lengths of lumber are more desirable and priced accordingly in the marketplace. By processing the quote from Seller A using routine 900, we arrive at a total MBF of 29.792, giving a total quoted price of $8,550.30. The selected metric price for the same types and quantities of lumber would be $8,471.12; therefore, the quoted price would have a percent of market value of 100.93%. Processing the quote from Seller B using routine 900, we arrive at a total MBF of 29.400, giving a total quoted price of $8,320.20. The selected metric price for the same types and quantities of lumber, however, would be $8,437.21; therefore, the quoted price would have a percent of market value of 98.61%. Finally, processing the quote from Seller C using routine 900, we arrive at a total MBF of 30.968, giving a total quoted price of $8,732.98. The selected metric price for the same types and quantities of lumber, however, would be $8,767.66; therefore, the quoted price would have a percent of market value of 99.38%. By looking at the percent of selected metric value, it is apparent that the price from Seller B is a better value. As shown in the methods of FIGS. 5-7, this price normalization process allows users to compare inherently different offers having different quality and quantity values.

In yet another example of an application of the normalization process, additional exemplary data is used to demonstrate the analysis of a transaction having one RFQ from a buyer and two different quotes from a seller, normalized to comparable product of another species. In this example, the buyer produces an RFQ listing the following items: one carload of Eastern SPF (ESPF) lumber having four units of 2″×4″×8′, four units of 2″×4″×10′, six units of 2″×4″×12′, two units of 2″×4″×14′, and six units of 2″×4″×16′. The vendor then responds with two different quotes with two different unit tallies and two different prices. The first response lists a quote price of $320 per thousand board feet, and a slight modification of the tally provides four units of 2″×4″×8′, four units of 2″×4″×10′, six units of 2″×4″×12′, three units of 2″×4″×14′, and five units of 2″×4″×16′. The second response quotes per the requested tally at a price of $322 per thousand board feet. Both quotes list the delivery location as “Chicago.”

To display the quotes, the server 230 produces a Web page similar to that displayed in FIG. 8C, where the vendor's modified tally is displayed in highlighted text. The buyer can then view a summary metric comparison or select the hypertext link “View Calculation Detail,” which then invokes the server 230 to produce a Web page as shown in FIG. 8D. Referring now to the Web page illustrated in FIG. 8D, the data produced by the server 230 compares the response to a selected metric of a different species, Western SPF (WSPF), for items of the same size, grade, and tally. The market price for the same 2×4 tally of ESPF and WSPF are thus simultaneously compared. In an example, Eastern quoted at $322 per thousand board feet, Western metric (Random Lengths™ 6/26/2000 print price plus freight of $80/M as defined in Metric Manager 435) for the same tally being $331.791. This metric comparison is also represented as Quote/Metric Value or Eastern price representing 0.970490, or 97% of comparable Western product.

In review of the normalization process, the buyer must select a metric source for price information for a defined item given a set of attributes, i.e., grade, species, and size. The metric may then be mapped to the RFQ item for comparison and does not have to be the equivalent of the item. For instance, as explained in the above-described example, it may be desirable to map the market relationship of one commodity item to another. The most current pricing data for the metric is electronically moved from the selected source to the server 230. As mentioned above, metric data may come from publicly available information, (i.e., price of futures contracts traded on the Chicago Mercantile Exchange), or subscription services, (i.e., Crowes™ or Random Lengths™ publications), or be an internal metric generated by the server 230. This metric data is used in the normalization process for all calculations, as described with reference to the above-described methods.

While various embodiments of the invention have been illustrated and described, it will be appreciated that within the scope of the appended claims, various changes can be made therein without departing from the spirit of the invention. For example, in an agricultural commodity, an order for Wheat U.S. #2 HRW could be compared to a selected metric of Wheat U.S. #2 Soft White, similar to how different species are analyzed in the above-described example.

The above system and method can be used to purchase other commodity items, such as in the trade of livestock. In such a variation, order information such as a lumber tally would be substituted for a meat type, grade, and cut. Other examples of commodity items include agricultural products, metals, or any other items of commerce having several order parameters. 

The invention claimed is:
 1. In a networked environment, a system comprising: at least one server that includes: a network interface; a processor in communication with the network interface and a non-transitory computer-readable medium having computer-executable instructions stored thereon, wherein execution of the computer-executable instructions by the processor implements system components including at least: a governing logic component comprising a metric server adapter programmed to manage a plurality of predefined instructions that pertain to at least one evaluation service or to metric data used to provide the at least one evaluation service, including domain or industry or user-agent specific instructions, and to define context-specific instructions for adapting the metric data; and a production component comprising a metrics application programmed to manage execution of the at least one evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the at least one server; wherein, at a predefined time or interval of time or in response to a triggering event, the at least one server is configured to implement the at least one evaluation service, which causes the production component to: obtain time-dependent metric data from at least one data source accessible to the at least one server, wherein the obtained metric data comprises market reference data, including price data for one or more items in a marketplace, the one or more marketplace items having attributes that are responsive to attributes identified for a target item defined by a set of attributes that includes two or more parameter values; evaluate the attributes of each marketplace item relative to the set of attributes that define the target item to dynamically discover relationships within the attribute data, wherein discovery of at least one relationship comprising a difference enables the governing logic component to contextually define one or more context-specific instructions for adapting the market reference data for a marketplace item having attributes that differ by at least one parameter value from the corresponding attributes identified for the target item; execute the context-specific instructions, wherein execution of at least one context-specific instruction causes one or more adjustment values to be applied to the market reference data for the marketplace item that differs, automatically transforming the market reference data for the marketplace item into normalized metric data for the target item; and produce, for the target item, one or more metric values for one or more metrics that pertain to the at least one evaluation service, wherein each metric value is produced, at least in part, using the normalized metric data for the target item.
 2. The system of claim 1, wherein coordinated operation of the production component and the governing logic component enables the at least one server to transform the market reference data for the at least one marketplace item that differs into normalized metric data for the target item without relying on a previously learned and constructed model having predefined relations that remain fixed within the model, or on a map identifying all possible relationships, or limiting available metric data to marketplace items that were previously mapped or modeled, or requiring contemporaneous user-agent instruction.
 3. The system of claim 1, wherein the production component algorithmically processes the attributes of the marketplace item and the set of attributes defined for the target item to dynamically discover relationships within the attribute data, wherein a discovered relationship can include a new or previously unknown relationship, and wherein discovery of one or more relationships comprising a difference enables the governing logic component to systematically process the set of attributes defined for the target item, each of the discovered relationships comprising a difference, and the plurality of predefined instructions that pertain to the at least one evaluation service, to ascertain which, if any, of the predefined instructions are applicable to the marketplace item in an immediate context identified for the target item, wherein coordinated operation of the production component and the governing logic component enables the governing logic component to contextually evolve context-specific instructions for adapting the metric data, wherein the context-specific instructions defined for the marketplace item are a function of the set of attributes identified for the target item and embody more than the predefined instructions that pertain to the at least one evaluation service.
 4. The system of claim 1, wherein the production component is further programmed to store at least one metric value produced for the target item, in association with the set of attributes that define the target item and the time or period of time of the obtained time-dependent metric data, in at least one data storage memory accessible to the at least one server.
 5. The system of claim 1, wherein the production component is programmed to manage one or more user interfaces that, in operation, facilitate interactions that enable the at least one server to expose to at least one computing device, via the network interface, at least one of the one or more metric values produced for the target item.
 6. The system of claim 1, wherein the production component is further programmed to manage one or more user interfaces that, in operation, enable the at least one server to expose at least one metric value produced for the target item to at least one preprogrammed application, utility, or function that is running on at least one computing device in communication with the at least one server, and to execute movement of data in an integrated data exchange between the at least one server and the at least one computing device, via the network interface, wherein the integrated data exchange does not include a pre-structured electronic data interchange (EDI) transmission.
 7. The system of claim 1, wherein transforming the market reference data for the marketplace item into normalized metric data for the target item occurs independent of routine data management protocols, wherein the data management protocols pertain to pre-processing data for use by the at least one server, including data validation, data extraction, data cleansing, and manipulating the form or format of the metric data as required to load the market reference data into a data storage memory accessible to the at least one server.
 8. The system of claim 1, wherein the predefined instructions that pertain to the at least one evaluation service were not predefined for, or pre-mapped to, a particular item in the marketplace.
 9. The system of claim 1, wherein each metric that pertains to the at least one evaluation service is pre-defined in one or more algorithms that are associated with the particular metric and at least one evaluation service, wherein implementation of the at least one evaluation service further causes the production component to produce the metric value for the particular metric by inserting at least a subset of the normalized metric data for the target item, as data input, into one or more of the algorithms associated with the particular metric and the implemented evaluation service.
 10. In a networked environment, a method comprising: obtaining, by at least one server, time-dependent metric data from at least one data source accessible to the at least one server, wherein the at least one server is operating under control of computer-executable instructions that, when executed by a processor, implement a plurality of system components including at least a governing logic component and a production component, wherein the obtained metric data comprises market reference data, including price data, for one or more items in a marketplace, the one or more marketplace items having attributes that are responsive to attributes identified for a target item defined by a set of attributes that includes two or more parameter values; and implementing, by the production component, at least one evaluation service that, in operation, includes: evaluating the attributes of each marketplace item relative to the set of attributes that define the target item to dynamically discover relationships within the attribute data, wherein discovery of at least one relationship comprising a difference enables the governing logic component to contextually define one or more context-specific instructions for adapting the market reference data for a marketplace item having attributes that differ by at least one parameter value from the corresponding attributes identified for the target item; executing the context-specific instructions, wherein execution of at least one context-specific instruction causes one or more adjustment values to be applied to the market reference data for the marketplace item that differs, automatically transforming the market reference data for the marketplace item into normalized metric data for the target item; and producing, for the target item, one or more metric values for one or more metrics that pertain to the at least one evaluation service, wherein each metric value is produced, at least in part, using the normalized metric data for the target item.
 11. The method of claim 10, wherein the governing logic component comprises a metric server adapter that includes one or more applications, application layers, or modules programmed to manage a plurality of predefined instructions that pertain to the at least one evaluation service or to the metric data used to provide the at least one evaluation service, including domain or industry or user-agent specific instructions, and to define context-specific instructions for adapting the metric data.
 12. The method of claim 10, wherein the production component comprises a metrics application that includes one or more applications, application layers, or modules programmed to manage the execution of the at least one evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the at least one server.
 13. The method of claim 10, wherein coordinated operation of the production component and the governing logic component enables the at least one server to transform the market reference data of a marketplace item that differs into normalized metric data for the target item without relying on a previously learned and constructed model having predefined relations that remain fixed within the model, or on a map identifying all possible relationships, or limiting the available metric data to marketplace items that were previously mapped or modeled, or requiring contemporaneous user-agent instruction.
 14. The method of claim 10, wherein the application of one or more adjustment values to the market reference data for the marketplace item concomitantly changes one or more relationships within the attribute data, wherein further discovery by the production component of at least one relationship comprising a difference triggers the production component to disclose the at least one newly discovered difference to the governing logic component, which enables the governing logic component to further define one or more context-specific instructions in response to the at least one newly discovered difference, wherein the production component executes the context-specific instructions defined by the governing logic component until the marketplace item in the obtained metric data (1) achieves a condition of acceptable alignment with the target item and the adjusted market reference data for the responsive item is used, or (2) is excluded from use for failure to meet a condition of acceptable alignment with the target item.
 15. The method of claim 10, wherein implementation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service further causes the production component to manage the obtained metric data for collective satisfaction of one or more validation rules and/or statistical criteria, including at least one of: a total volume of responsive marketplace items; a frequency or liquidity of marketplace items; a concentration or fragmentation of the marketplace items by transaction type; or a concentration or fragmentation of the marketplace items by the source of the metric data, wherein the market reference data of the marketplace items in the obtained metric data is collectively determined to satisfy the one or more validation rules and/or statistical criteria and is used, or is collectively determined to not satisfy the one or more validation rules and/or statistical criteria and is excluded from use.
 16. The method of claim 10, wherein each metric that pertains to the at least one evaluation service is predefined in one or more algorithms that are associated with the particular metric and at least one evaluation service and stored in at least one memory accessible to the at least one server, wherein implementation of the at least one evaluation service causes the production component to produce the metric value for the particular metric by inserting at least a subset of the normalized metric data for the target item, as data input, into one or more of the predefined algorithms associated with the particular metric and the implemented evaluation service.
 17. The method of claim 10, wherein the obtained metric data includes a plurality of market transaction data sets previously exposed by at least one buyer-agent or at least one seller-agent, wherein each obtained market transaction data set is responsive to attributes identified for the target item, and wherein the obtained metric data may include market transaction data that was previously aggregated in one or more data storage memories and exposed to the at least one server by a third-party, via the network interface.
 18. The method of claim 10, wherein the production component is further programmed to manipulate the form or format of one or more of the metric values produced for the target item before loading the metric values into a stylized template or document, wherein at a predefined time or a predefined period of time or in response to a triggering event, the production component is further programmed to manage one or more user interfaces that, in operation, enable the at least one server to expose to at least one computing device in communication with the at least one server or at least one output defined in at least one predefined instruction that pertains to the at least one evaluation service one or more of the metric values produced for the target item, and wherein one or more of the user interfaces cause a receiving computing device to display the exposed metric values in a stylized and unified presentation.
 19. The method of claim 16, wherein at least one predefined algorithm associated with the at least one evaluation service comprises a replicable mathematical process for determining a mean value, a median value, or variation of a mean or median.
 20. The method of claim 10, further comprising producing, by the production component, at least one metric price that comprises a range of market price data values for the target item.
 21. The method of claim 10, further comprising producing, by the production component, one or more metric values for the target item over a series of times or delivery dates, wherein the series of times or delivery dates can include one or more dates in the future, and wherein the metric values provide a price curve or trend line for the target item.
 22. The method of claim 10, wherein implementation of the at least one evaluation service or execution of at least one predefined instruction that pertains to the at least one evaluation service further causes the production component to monitor for a change in one or more of the metric values produced for the target item, wherein if one or more of the metric values exceeds or falls below a predefined threshold deviation from a corresponding metric value previously produced for the target item, or a predefined base value, or a predefined range of values, the production component is further caused to flag the one or more metric values, and/or to trigger an automatic alert to be communicated to at least one output specified in at least one of the predefined instructions that pertain to the at least one evaluation service, and wherein the production component is further programmed to manage one or more user interfaces that, in operation, expose the alert to the at least one output.
 23. The method of claim 10, further comprising obtaining, by the production component, at a predefined time or interval of time or in response to a triggering event, more-current metric data for the target item from at least one data source accessible to the at least one server, and/or excluding previously-obtained market reference data for a marketplace item having attributes that no longer correspond to the attributes identified for the target item, wherein the production component, operating in coordination with the governing logic component, automatically produces one or more more-current metric values for the target item, and wherein an interval of time can include a continuously sliding interval of time that represents a most current period of time.
 24. The method of claim 10, wherein one or more parameter values include at least one of a grade, a rating measure, a species or classification, an item type, a brand, a size, a style or design, a unit of measure, a tally, a quantity, a price, a weight, a shipping or receiving location, a method of delivery, a delivery date or time of service, a warranty, a capacity or performance measure, a payment term, or a transaction type.
 25. The method of claim 24, wherein the delivery date or time of service specifies one or more fulfillment dates in the future, and comprises a forward price transaction type.
 26. The method of claim 24, wherein delivery comprises a financial delivery.
 27. The method of claim 10, wherein the target item defined by a set of attributes that includes two or more parameter values represents a specific version or particular form of a physical product, a raw material, an intangible product, a service, or a combination thereof.
 28. The method of claim 10, wherein the target item comprises a bundle of items or a packaged product that includes a plurality of items or component parts having attributes that differ by at least one parameter value, and wherein each metric value for the target item is produced, at least in part, using the normalized metric data for each of the plurality of items or component parts in the bundle of items or the packaged product.
 29. The method of claim 10, wherein the target item comprises a packaged product that specifies an exchange of at least one item defined by a set of attributes for at least one other item defined by a set of attributes, wherein the other item differs by at least one parameter value from the attributes identified for the at least one item, and wherein at least one metric value produced for the target item comprises the value of the difference between at least one metric value produced for the at least one item and a corresponding metric value produced for the at least one other item.
 30. The method of claim 10, wherein the obtained metric data comprises previously processed market reference data, including price data, for a particular marketplace item having attributes that are responsive to attributes identified for the target item, wherein the particular marketplace item is predefined by a set of attributes that includes two or more parameter values in one or more rules established by a regulated exchange, a trading venue or a price reporting service.
 31. The method of claim 10, further comprising managing, by the production component, one or more user interfaces that, in operation, facilitate interactions that enable a user-agent computing device in communication with the at least one server to enter at least one domain, industry or user-agent specific instruction that defines a metric, wherein the user-agent is enabled to identify or select assessment variables and to specify one or more functions or algorithms with which to produce the user-agent defined metric, and to associate the metric with at least one evaluation service, and wherein at least one of the one or more user interfaces further enables the user-agent computing device to further associate evaluation criteria with the user-agent defined metric and/or to specify one or more data inputs required to produce the metric value, wherein the production component is further programmed to save the user-agent predefined instruction in association with, at least, the specific domain, industry or user-agent and the at least one evaluation service, in at least one data storage memory accessible to the at least one server.
 32. The method of claim 10, wherein implementation of the at least one evaluation service and/or execution of one or more of the predefined instructions that pertains to the at least one evaluation service further causes the production component, at a predefined time or interval of time or in response to a triggering event, to evaluate the performance of two or more metric values previously produced for the target item, wherein the production component is programmed to automatically obtain from one or more data sources accessible to the at least one server, time-dependent market reference data representing consummated marketplace transactions, including price data, for the target item, and to compare the price data identified in one or a combination of the consummated marketplace transactions to each metric value previously produced for the target item, wherein the comparison enables the evaluation service, or at least one user-agent computing device in communication with the at least one server, to ascertain which of the previously-produced metrics most accurately predicted the price paid for the target item in the marketplace.
 33. The method of claim 10, further comprising managing, by the production component, one or more user interfaces that, in operation, facilitate interactions that enable a user-agent computing device in communication with the at least one server to predefine at least one domain, industry or user-agent specific instruction for the at least one evaluation service, wherein at least one of the one or more user interfaces enables the user-agent to identify or select a set attributes including two or more parameter values to define a target item, and to associate the instruction with at least one particular domain, industry or user-agent, and further enables the user-agent computing device to associate the target item with one or more other items or item types or transaction types, and wherein the production component is further programmed to store the at least one user-agent predefined instruction in association with, at least, the set of attributes that define the target item, at least one domain, industry or user-agent and the at least one evaluation service, in at least one data storage memory accessible to the at least one server.
 34. The method of claim 33, wherein one or more of the user interfaces, in operation, further enables the user-agent computing device to identify and associate a unique label or code with the user-agent defined target item, and/or to cause one or more sources of metric data, or at least one other predefined instruction that pertains to the at least one evaluation service, to be associated with the user-agent defined target item.
 35. The method of claim 10, wherein at least one context-specific instruction defined by the governing logic component is expressed as “IF condition THEN action”, wherein the production component; is caused to conditionally manage the application of one or more adjustment values to the market reference data for the marketplace item.
 36. The method of claim 10, further comprising filtering, by the production component, the marketplace items in the obtained metric data for inclusion or exclusion using one or more predefined control values, criteria, and/or parameter values specified in one or more of the predefined instructions that pertain to the at least one implemented evaluation service.
 37. The method of claim 10, wherein the production component is programmed to query; a plurality of databases or data sources accessible to the at least one server or to monitor one or more data streams to obtain the metric data for the target item.
 38. The method of claim 37, wherein the production component is further programmed to pre-process the accessible metric data using one or more data management protocols, wherein the data management protocols pertain to the pre-processing of the metric data for use by the at least one server, including data validation, data extraction, data cleansing, or manipulating the form or format of the metric data as required to load the metric data into a data storage memory accessible to the at least one server, and wherein the transformation of the market reference data for a responsive marketplace item that differs into normalized metric data for the target item occurs independent of the one or more data management protocols.
 39. The method of claim 10, wherein the production component is further programmed to convert data defined by a unit of measure into standardized or common units of measure and to use only data possessing consistent units of measure to produce the one or more metric values for the target item, wherein the transformation of the market reference data for the at least one marketplace item that differs occurs independent of the unit-of-measure conversion of data defined by a unit of measure.
 40. The method of claim 10, wherein at least one predefined instruction that pertains to the at least one evaluation service associates the target item with at least one alternate item, wherein the alternate item is a different item and/or a substitute item for the target item, wherein each alternate item is identified by a set of attributes that includes two or more parameter values, wherein, in operation, the production component is caused to obtain time-dependent metric data from at least one data source accessible to the at least one server, wherein the obtained metric data represents market reference data, including price data, for one or more marketplace items having attributes that are responsive to attributes identified for the at least one alternate item, and wherein the governing logic component uses the market reference data for the alternate item to define one or more context-specific instructions for adapting the market reference data for the alternate item, wherein execution of the context-specific instruction causes the production component to apply a formula, rule or correlation to the market reference data for the alternate item, transforming the market reference data for the alternate item into normalized metric data for the target item.
 41. The method of claim 10, wherein at least one context-specific instruction defined by the governing logic component causes the production component to use one or more curve-fit algorithms to generate one or more of the adjustment values to be applied to the market reference data for a responsive item that differs, wherein each adjustment value serves to minimize a difference between a parameter value identified for the marketplace item that differs and (1) an average of the marketplace items in the obtained metric data having attributes that correspond to the set of attributes defined for the target item, or (2) an average value for the at least one parameter derived from a control group.
 42. The method of claim 16, wherein at least one metric that pertains to the at least one evaluation service further causes the production component to retrieve one or more metric values previously produced for the target item, or a predefined base value, or one or more time-dependent market price data values reported by an exchange or trading venue or one or more other evaluation services or price reporting services, wherein the retrieved data is further inserted, as data inputs, into one or more of the predefined algorithms, associated with the particular metric and the implemented evaluation service, to produce the at least one metric value.
 43. The method of claim 10, further comprising producing, by the production component, documentation that enables an audit of a previously-produced metric value, wherein the production component, operating in coordination with the governing logic component, is programmed to document the data and process steps used to transform the market reference data for the at least one marketplace item into normalized metric data for the target item by replicating the process steps of the at least one evaluation service using the data that was previously used in each process step, and to manage one or more user interfaces that, in operation, enable the at least one server to communicate, via the network interface, the documentation to one or more computing devices in communication with the at least one server or at least one output specified in at least one predefined instruction that pertains to the at least one evaluation service.
 44. The method of claim 12, further comprising managing, by the production component, one or more user interfaces that, in operation, facilitate data communications in XML format, enabling the production component to dynamically change, dynamically route, and/or pre-configure the data for movement in an integrated data exchange.
 45. The method of claim 10, wherein implementation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service further causes the production component to obtain only metric data resulting from a computer-based interaction or to use only market reference data resulting from electronically-created market transaction data to produce the one or more metric values for the target item, wherein the electronically-created market reference data includes data comprising a timestamp that identifies the particular time or period of time, and wherein the obtained metric data does not include human-reported market transaction data that was manually transcribed into a digital format.
 46. The method of claim 10, wherein the plurality of predefined instructions that pertain to the at least one evaluation service include one or more domain or industry specific instructions and/or one or more user-agent specific instructions, wherein the coordinated operation of the production component and the governing logic component enables the production component to manage the execution of the at least one evaluation service in a manner that is customized for the user-agent and/or the domain and/or the industry, and to produce one or more metric values that are customized for the user-agent and/or the domain and/or industry, wherein the coordinated operation of the production component and the governing logic component enables the customized evaluation service to be accomplished without custom-coding the computer-executable instructions that comprise the production component.
 47. In a networked environment, a non-transitory computer-readable medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed by a processor of at least one server, causes the at least one server to implement a plurality of system components including at least a governing logic component and a production component, and to perform operations comprising: obtaining, by the at least one server, time-dependent metric data from at least one data source accessible to the at least one server, wherein the obtained metric data comprises market reference data, including price data, for one or more items in the marketplace, the one or more marketplace items having attributes that are responsive to attributes identified for a target item defined by a set of attributes that includes two or more parameter values; and implementing at least one evaluation service, wherein the computer-executable instructions cause the production component of the at least one server to: evaluate the attributes of each marketplace item relative to the set of attributes that define the target item to dynamically discover relationships within the attribute data, wherein discovery of at least one relationship comprising a difference enables the governing logic component to contextually define one or more context-specific instructions for adapting the market reference data for a marketplace item having attributes that differ by at least one parameter value from the corresponding attributes identified for the target item; execute the context-specific instructions, wherein execution of at least one context-specific instruction causes one or more adjustment values to be applied to the market reference data for the marketplace item that differs, automatically transforming the market reference data for the marketplace item into normalized metric data for the target item; and produce, for the target item, one or more metric values for one or more metrics that pertain to the at least one evaluation service, wherein each metric value is produced, at least in part, using the normalized metric data for the target item.
 48. The computer-readable medium of claim 47, wherein the computer-executable instructions, when executed, cause the production component to manage the execution of the at least one evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the at least one server.
 49. The computer-readable medium of claim 47, wherein the computer-executable instructions, when executed, cause the governing logic component to manage a plurality of predefined instructions that pertain to the at least one evaluation service or to the metric data used to provide the at least one evaluation service, including domain or industry or user-agent specific instructions, and to define context-specific instructions for adapting the metric data.
 50. The computer-readable medium of claim 47, wherein the computer-executable instructions, when executed, cause the production component to execute at least one context-specific instruction defined by the governing logic component that causes one or more adjustment values to be applied to the market reference data for a marketplace item that differs, concomitantly changing one or more relationships within the attribute data for the marketplace item and target item, wherein further discovery, by the production component, of one or more relationships comprising a difference enables the governing logic component to further define one or more context-specific instructions in response to the at least one newly-discovered difference, wherein the production component executes the context-specific instructions defined by the governing logic component until the responsive marketplace item in the obtained metric data (1) achieves a condition of acceptable alignment with the target item and the adjusted market reference data for the marketplace item is used, or (2) is excluded from use for failure to meet a condition of acceptable alignment with the target item. 